This toolkit includes everything you need to build your own KeyQuencer extensions.
- The "Extension.h" file provides all the knowledge and interface specifications you need to build a working extension with any C compiler. This is the only file you need if you are an expert programmer and want to write all of the code yourself. Note that the header already includes support for features that are only available with KeyQuencer 2.0.
- The "Extension.c" and "Action.h" files contain a simple extension frame that can be used without changes for any extension. The "A4Globals.h" header deals with compiler-specific ways to access global variables (the 68K Think C and Code Warrior environments are currently supported).
- The "KQGestalt.c", "KQGestalt.h" and "INITGestalt.h" files provide a standard way to get a pointer to the KeyQuencer glue from an external piece of code (KeyQuencer extensions don't need these files since they receive the glue pointer as a parameter). Using these files makes your software compatible with both the current shareware version and the upcoming KeyQuencer 2.0. The "KQPPCGlue.h" header contains mixed-mode procedure information for some of the KeyQuencer glue routines, so that they can be called from native applications. Open the "GlueSample.c" source file to learn how to call the glue routines in a way that works with both 68K and PowerPC compilers.
- "Action.c" and "Sample.rsrc" are the only files to change if you want to build a KeyQuencer extension using the standard extension frame. Just insert your code in the init() and run() routines (read the "Action.h" file for more information about them), edit the 'MPRM' resource with the provided ResEdit template and change the code resource name to match your extension's name. You should also remove the 'cicn', 'ICN#' and 'TEXT' resources from the "Sample.rsrc" file if you're not using them.
- The "Sample-TC.π" file is a Think C 7 project. If you have an older version of the compiler and can't read the project, create a new one and add "Action.c", "Extension.c", "Sample.rsrc" and "MacTraps". Set the project type to "Code resource", file type 'KQex', creator 'KQue', name "Sample" (or your own extension's name), resource type 'KQex', ID 128 (or any other), attributes none (00).
- The "Sample-CW.π" file is a Code Warrior 7 project. You may build a new one if needed by adding the same files described above and setting the project preferences accordingly.
The "GlueSample.π", "GlueSample68K.π" and "GlueSamplePPC.π" projects let you build a small application with Think C 7 and Code Warrior 7 respectively. The glue sample shows how to interface to the KeyQuencer glue from an external piece of code such as a standalone application and how to use the new callback routines introduced in KQ 1.2.2 to get a list of all the installed macros.
